home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
SGI Origin & Onyx2 Patches 1998 May
/
Origin and Onyx2 System Disk Patches May 1998.img
/
relnotes
/
patchSG0002600
/
ch1.z
/
ch1
Wrap
Text File
|
1998-04-22
|
8KB
|
265 lines
- 1 -
1. _P_a_t_c_h__S_G_0_0_0_2_6_0_0__R_e_l_e_a_s_e__N_o_t_e
This release note describes patch SG0002600 to IRIX 6.4.
1.1 _S_u_p_p_o_r_t_e_d__H_a_r_d_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for IP27 and IP30 systems.
The software cannot be installed on other configurations.
1.2 _S_u_p_p_o_r_t_e_d__S_o_f_t_w_a_r_e__P_l_a_t_f_o_r_m_s
This patch contains bug fixes for IRIX6.4 (version
1263561140). The software cannot be installed on other
configurations.
1.3 _B_u_g_s__F_i_x_e_d__b_y__P_a_t_c_h__S_G_0_0_0_2_6_0_0
This patch contains fixes for the following bugs in IRIX
6.4. Bug numbers from Silicon Graphics bug tracking system
are included for reference.
+o In Failsafe, SP failure followed by node failure can
cause XLV on the peer node to not see the alternate
path to the RAID. Also, when disks are migrated from
more than 5 different systems, the XLV tools (xlv_make,
xlv_mgr, ...) dump core. (bug# 468493)
+o XLV doesn't process multiple plex errors correctly when
receiving many disk errors, and can cause a kernel
panic. (bug# 528089)
+o A root volume which is either concatenated or striped
isn't properly rejected at boot time. (bug# 532078)
+o xlv_mgr(1m) doesn't handle volumes with duplicate names
but different hostnames. (bug# 533693)
+o The death of the xlv_labd(1m) process can cause the
kernel to hang. We work around this by restarting the
deamon as necessary. (bug# 534748)
+o Under heavy load, XLV created a stale reference to a
buffer, causing a kernel panic. (bug# 536379)
+o On a system with a large number of disks, xlv_make(1m)
is slow in creating the object after the user finishes
the object definition. (bug# 539826)
This patch also "rolls up" patch 1841 that fixes the bugs
- 2 -
list below:
+o Xlv_make(1m) is not validating that a completed volume
has the required data subvolume. (bug# 424780)
+o A bug in fifofs was causing data to get stuck in pipes.
The bug was fixed in the base 6.4 release, but the XLV
workaround for it wasn't removed. This removes the now
unneeded workaround. (bug# 441978)
+o xlv_mgr(1m) can silently fail to delete an object when
a disk has a few partitions that are part of multiple
XLV objects. Only the first delete succeeds, and
further attempts fail. (bug# 461915)
+o XLV performs poorly when a large number of volumes are
configured. XLV now adapts to system load. Also added
a command to xlv_mgr(1m) to change the memory pool
parameters. (bug# 464653)
+o When xlv_mgr(1m) is started by non-root, a device
number could not be mapped to an alias /dev/dsk device
pathname and the misleading message "Unnamed device" is
used. The problem is in libdisk but xlv_mgr(1m) should
at least display the hardware graph device pathname.
(bug# 465221)
+o xlv_shutdown(1m) now skips updating single plexed
volumes. This makes shutdown more efficient since it
can skip the disk label update with no loss of
information because XLV treats the 'active' and 'clean'
states the same for volumes with only one plex. (bug#
467132)
+o During system startup, if /tmp is a volume and there
are plexed volumes being revived, the mount of the /tmp
volume fails. /tmp cannot mount until all the plexed
volumes are revived. (bug# 471909)
+o During a XLV plex revive, a read error on the source
volume element causes the system to panic with a kernel
fault. (bug# 474748)
+o Attaching a plex or ve to a non-local object can cause
the nodename associated with the volume to revert to
the current host. (bug# 486367)
+o Fixed a timing window when growing a plex while a
revive was already in progress. Under some
circumstances, the outstanding i/o would never get
issued, and cause those processes to hang waiting for
- 3 -
the I/O to complete. (bug# 497628)
1.4 _S_u_b_s_y_s_t_e_m_s__I_n_c_l_u_d_e_d__i_n__P_a_t_c_h__S_G_0_0_0_2_6_0_0
This patch release includes these subsystems:
+o patchSG0002600.eoe_sw.unix
+o patchSG0002600.eoe_sw.xlv
+o patchSG0002600.eoe_sw.xlvplex
1.5 _I_n_s_t_a_l_l_a_t_i_o_n__I_n_s_t_r_u_c_t_i_o_n_s
Because you want to install only the patches for problems
you have encountered, patch software is not installed by
default. After reading the descriptions of the bugs fixed
in this patch (see Section 1.3), determine the patches that
meet your specific needs.
If, after reading Sections 1.1 and 1.2 of these release
notes, you are unsure whether your hardware and software
meet the requirements for installing a particular patch, run
_i_n_s_t. The _i_n_s_t program does not allow you to install
patches that are incompatible with your hardware or
software.
Patch software is installed like any other Silicon Graphics
software product. Follow the instructions in your _S_o_f_t_w_a_r_e
_I_n_s_t_a_l_l_a_t_i_o_n _A_d_m_i_n_i_s_t_r_a_t_o_r'_s _G_u_i_d_e to bring up the miniroot
form of the software installation tools.
Follow these steps to select a patch for installation:
1. At the Inst> prompt, type
iiiinnnnssssttttaaaallllllll ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
2. Initiate the installation sequence. Type
IIIInnnnsssstttt>>>> ggggoooo
3. You may find that two patches have been marked as
incompatible. (The installation tools reject an
installation request if an incompatibility is
detected.) If this occurs, you must deselect one of
the patches.
- 4 -
IIIInnnnsssstttt>>>> kkkkeeeeeeeepppp ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
4. After completing the installation process, exit the
_i_n_s_t program by typing
IIIInnnnsssstttt>>>> qqqquuuuiiiitttt
1.6 _P_a_t_c_h__R_e_m_o_v_a_l__I_n_s_t_r_u_c_t_i_o_n_s
To remove a patch, use the _v_e_r_s_i_o_n_s _r_e_m_o_v_e command as you
would for any other software subsystem. The removal process
reinstates the original version of software unless you have
specifically removed the patch history from your system.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeee ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
To keep a patch but increase your disk space, use the
_v_e_r_s_i_o_n_s _r_e_m_o_v_e_h_i_s_t command to remove the patch history.
vvvveeeerrrrssssiiiioooonnnnssss rrrreeeemmmmoooovvvveeeehhhhiiiisssstttt ppppaaaattttcccchhhhSSSSGGGG_x_x_x_x_x_x_x
where _x_x_x_x_x_x_x is the patch number.
1.7 _K_n_o_w_n__P_r_o_b_l_e_m_s